-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow fakers to build on previously populated fields. #420
Conversation
6250df2
to
58d3411
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a video call where we went over a few small changes. Let me know when you've done them and I'll make a final pass. Otherwise, this looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After having gone over the code with Paul, and seeing these last few changes, I'm satisfied.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are any updates to documentation needed?
@davisagli : I think I'd just consider this "making fake data more realistic" and not needing of docs unless it causes some confusion or problem for someone. I'll also wait on documenting the new plugin local variables feature until someone asks for a "feature like local variables for plugins". Premature documentation locks me into a particular interface. |
Allow fakers to build on previously populated fields, such as emails based on firstnames.
Currently: Emails and Usernames are based on FirstNames and LastNames.
Also adds a bit of test coverage.